Added ranger audit configuration example for Elastic Search #26692
Conversation
|
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
jonashartwig
changed the title
|
Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla |
|
Hi, I signed and sent the CLA. Anything went wrong? |
|
Hi, the CLA process usually takes about 1 - 2 weeks, no worries |
|
Hi, apologies for my impatience. It is signed and accepted now. regards |
|
|
||
| * Access to a Apache Ranger deployment with the desired authorization policies. | ||
| * Access to an audit store using Solr, HDFS, Log4J, or S3 to save audit logs. | ||
| * Access to an audit store using Solr, HDFS, Log4J, Elastic Search, or S3 to save audit logs. |
There was a problem hiding this comment.
Elastic Search -> Elasticsearch
3 participants
Description
This PR adds examples on how to configure audit with elastic search. It extends the existing docs.
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text: